Changing code execution path using kernel mode redirection

ABSTRACT

A mechanism for redirecting a code execution path in a running process. A one-byte interrupt instruction (e.g., INT 3) is inserted into the code path. The interrupt instruction passes control to a kernel handler, which after executing a replacement function, returns to continue executing the process. The replacement function resides in a memory space that is accessible to the kernel handler. The redirection mechanism may be applied without requiring a reboot of the computing device on which the running process is executing. In addition, the redirection mechanism may be applied without overwriting more than one byte in the original code.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No. 11/177,079 filed on Jul. 8, 2005, and of U.S application Ser. No. 10/681,017, filed on Oct. 8, 2003.

BACKGROUND OF THE INVENTION

It is often desirable to change a code execution path in a running process without changing the original on-disk image of the executing modules or without requiring a restart of the computer. One way to accomplish this is via a “Hotpatching” mechanism. Hotpatching is in-memory patching mechanism that enables the installation of software updates without requiring users to restart their computers by automatically inserting code from a software update into a running process. This means that system files can be updated while they are in use.

For example, Hotpatching may bypass a vulnerable function in a running process by injecting a JMP instruction at the beginning of the vulnerable function. When the function is called, it jumps to a new function that is also loaded into the process space by the Hotpatching mechanism. The problem with this approach is that an injected JMP instruction may overwrite multiple instructions in a way that leads to unexpected behavior. In the Hotpatching case, if the beginning of the vulnerable function includes 3 assembly opcodes in the first 5 bytes (1 byte opcode, 2 bytes opcode, 2 bytes opcode), the JMP injection will replace all five bytes. If the processor is executing the first byte opcode, and the injection has changed the next two opcodes, unexpected processor behavior may result.

SUMMARY OF THE INVENTION

One aspect of the invention provides a mechanism for redirecting a code execution path in a running process. A one-byte interrupt instruction (e.g., INT 3) is inserted into the code path. The interrupt instruction passes control to a interrupt handler, which after executing replacement functionality returns to continue executing the process. The replacement functionality resides in a memory space that is accessible to the interrupt handler, for example in memory or in an encrypted software license. The redirection mechanism may be applied without requiring a reboot of the computing device on which the running process is executing. In addition, the redirection mechanism may be applied without overwriting more than one byte in the original code.

Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:

FIG. 1 is a block diagram showing an exemplary computing environment in which aspects of the invention may be implemented; and

FIG. 2 illustrates an exemplary system and method for redirecting a code execution path in a running process in accordance with the present invention.

FIG. 3 illustrates an exemplary system and method for redirecting a code execution path in a running process in a proxy execution environment in accordance with the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Exemplary Computing Environment

FIG. 1 illustrates an example of a suitable computing system environment 100 in which the invention may be implemented. The computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100.

The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.

With reference to FIG. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a computer 110. Components of computer 110 may include, but are not limited to, a processing unit 120, a system memory 130, and a system bus 121 that couples various system components including the system memory to the processing unit 120. The system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, Peripheral Component Interconnect (PCI) bus (also known as Mezzanine bus), Peripheral Component Interconnect Express (PCI-Express), and Systems Management Bus (SMBus).

Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and non-volatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

The system memory 130 includes computer storage media in the form of volatile and/or non-volatile memory such as ROM 131 and RAM 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation, FIG. 1 illustrates operating system 134, application programs 135, other program modules 136, and program data 137.

The computer 110 may also include other removable/non-removable, volatile/non-volatile computer storage media. By way of example only, FIG. 1 illustrates a hard disk drive 141 that reads from or writes to non-removable, non-volatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, non-volatile magnetic disk 152, and an optical disk drive 155 that reads from or writes to a removable, non-volatile optical disk 156, such as a CD-ROM or other optical media. Other removable/non-removable, volatile/non-volatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as interface 140, and magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150.

The drives and their associated computer storage media, discussed above and illustrated in FIG. 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer 110. In FIG. 1, for example, hard disk drive 141 is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. Note that these components can either be the same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers here to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 110 through input devices such as a keyboard 162 and pointing device 161, commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195.

The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in FIG. 1. The logical connections depicted include a local area network (LAN) 171 and a wide area network (WAN) 173, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 1 illustrates remote application programs 185 as residing on memory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

Exemplary Embodiments

One aspect of the present invention is directed to a mechanism for redirecting a code execution path in a running process in memory that does not lead to unexpected behavior by advantageously using a one-byte interrupt instruction (e.g., INT 3) that is inserted into the code path. The interrupt instruction passes control to a interrupt handler, which after executing a replacement function, returns to continue executing the process.

With reference to FIG. 2, there is illustrated an exemplary process 200 running in memory. In accordance with an embodiment of the present invention, an execution path 201 (e.g., the beginning of a vulnerable function to be replaced) of the process 200 running in memory may be changed by overwriting an existing instruction 202 with a one byte interrupt instruction (e.g., INT 3), where the remainder of the original code 203 remains unaltered. INT 3 is typically used as a trap to a debugger to break out of execution in order for other code to be executed.

The interrupt instruction will cause a interrupt handler 204 to be called. In one embodiment, the interrupt handler 204 may be running in kernel-mode, and as such may be alternatively referred to as a kernel handler. The interrupt handler/rights client 302 is depicted in the Figures in kernel mode memory space, although it will be appreciated that interrupt handler/rights client 302 could in some embodiments be implemented as a user mode process. The interrupt handler 204 for that interrupt includes a mechanism that will cause a return from the interrupt to continue into a new instruction 206 (e.g., the replacement function) instead of returning to the original function. The new instruction 206 is placed in a memory space known to the interrupt handler 204. Because the interrupt instruction is a one byte instruction, the present invention advantageously provides a mechanism for code diversion that need not overwrite more than one byte in the original code 203.

Another embodiment of the invention comprises changing code execution path in a setting including a “proxy execution” mechanism as described in U.S. patent application Ser. No. 10/681,017. In one embodiment, proxy execution comprises executing certain software functionality on behalf of a running process. This enables binding software to a software license. Some software functionality can only be allowed to execute by proxy execution, and a secure proxy validates a license prior to executing such functionality.

For example, one could ensure that the executable “MyLicensedSoftware.exe” can only function if the license “LicenseForSoftware.lic” is properly installed. To do so, parts of MyLicensedSoftware.exe may be encrypted, coupled to LicenseForSoftware.lic, and replaced by one or more placeholder instructions that invoke proxy execution. Proxy execution ensures the LicenseForSoftware.lic is available, then executes the encrypted parts of the MyLicensedSoftware.exe software on behalf of the MyLicensedSoftware.exe process.

With reference to FIG. 3, there is illustrated an exemplary system and method for redirecting a code execution path in a running process 300, evaluating a license 303 and optionally proxy executing code 305 coupled to the license 303. Process 300 may be running in user mode memory as will be appreciated by those of skill in the art. In accordance with an embodiment of the present invention, a function 301 associated with process 300 includes at least one INT3 instruction 304 that when executed will result in the interrupt handler/rights client 302 to being called. Thus, a first step in a method illustrated in FIG. 3 is that of (1) INT 3, wherein an interrupt instruction 304 triggers a call to an interrupt handler/rights client 302. Note that a function 301 may contain any number of interrupt instructions 304.

The second step of a method illustrated in FIG. 3 comprises (2) evaluate rights/execute functionality. The interrupt handler/rights client 302 for that interrupt instruction 304 can include a mechanism 306 that extracts functionality 305 from a license 303. In one embodiment, functionality 305 can be for the specific INT3 instruction 304 in the specific function 301 of process 300. In one embodiment, matching appropriate functionality 305 to process 300, function 301, and interrupt instruction 304 is a matter of retrieving an appropriate license 303 for software associated with process 300.

Thus interrupt handler/rights client 302, can, in one embodiment, comprise a rights client with a license evaluator 306, and can operate in connection with a product activation service or otherwise to control operation and use of an application based on a corresponding license 303 by executing code 305 on behalf of and as a proxy for process 300, but only if the license evaluator 306 determines that the license 303 allows such execution. Thus, the rights client 302 with the license evaluator 306 enforces the license 303 as against a user of an application corresponding to process 300.

Accordingly, the interrupt handler/rights client 302 may choose whether to in fact proxy execute the code 305 for the process 300 based, among other things, on whether the license evaluator 306 has access to a license 303 corresponding to the process 300, and on whether the license 303 has permissions or rights that allow or at least do not prohibit the action corresponding to the code 305 to be executed. While one function 305 is illustrated in FIG. 3, it should be appreciated that license 303 may comprise a table or other data structure comprising a plurality of functions, and license 303 may comprise appropriate permissions to access some or all of such functions, which may in turn be evaluated by rights license evaluator 306.

In one embodiment, the license 303 includes encoded information regarding the code 305 that the rights client 302 is to proxy-execute. In such an embodiment, the license 303 must be available to the rights client 302 in order for the rights client 302 to proxy-execute code 305 on behalf of the process 300. For example, the encoded information may include the code 305, a reference to a location of the code 305, a decryption key 308 for decrypting an encrypted version of the code 305, or the like.

Interrupt handler/rights client 302 can cause decryption of license 303 or portions thereof, such as code 305, prior to causing execution of code 305. In one embodiment, code 305 may be encrypted, and encryption/decryption key 308 may be required to decrypt code 305. Interrupt handler/rights client 302 can retrieve encryption/decryption key 308 and interact with an appropriate encryption/decryption mechanism 307 in order to decrypt code 305 prior to causing execution thereof.

In another embodiment, encryption/decryption key 308 can itself be encrypted with encryption/decryption key 309. Interrupt handler/rights client 302 can first retrieve encryption/decryption key 308, then decrypt it using encryption/decryption key 309 and, for example, encryption/decryption mechanism 307. Interrupt handler/rights client 302 can then retrieve encrypted code 305, decrypt and execute it as described above.

Following the execution of the code 305 from the license 303, the interrupt handler/rights client 302 can return to the appropriate address in the process 300 space in order to continue execution, as illustrated by step (3) return after proxy execution. The handler/rights client 302 can return to any location, as desired, including but not limited to alternative locations in a program.

While the present invention has been described in connection with the preferred embodiments of the various FIGS., it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiment for performing the same function of the present invention without deviating therefrom. For example, one skilled in the art will recognize that the present invention as described in the present application may apply to any computing device or environment, whether wired or wireless, and may be applied to any number of such computing devices connected via a communications network, and interacting across the network. Furthermore, it should be emphasized that a variety of computer platforms, including handheld device operating systems and other application specific operating systems are contemplated, especially as the number of wireless networked devices continues to proliferate. Still further, the present invention may be implemented in or across a plurality of processing chips or devices, and storage may similarly be effected across a plurality of devices. Therefore, the present invention should not be limited to any single embodiment, but rather should be construed in breadth and scope in accordance with the appended claims. 

1. A method of redirecting a code execution path in a running process, comprising: injecting a one-byte interrupt instruction into said code execution path of said process while said process is running, wherein said injecting comprises overwriting an instruction associated with said running process, said instruction existing in memory; passing control to a kernel handler upon execution of said one-byte interrupt instruction; executing a replacement function called by said kernel handler; and returning to said running process.
 2. The method of claim 1, wherein said one-byte interrupt instruction is an INT 3 interrupt instruction.
 3. The method of claim 1, wherein said kernel handler includes a mechanism to cause a return from said interrupt instruction to continue into said replacement function.
 4. The method of claim 1, further comprising inserting said one-byte interrupt instruction such that no more than one byte of the original code in said code execution path is overwritten.
 5. The method of claim 1, further comprising loading said replacement function into a memory space accessible by said kernel handler.
 6. The method of claim 1, further comprising evaluating a license prior to executing said replacement function.
 7. The method of claim 1, further comprising decrypting said replacement function.
 8. A method of changing a code execution path by using a one-byte interrupt to replace an existing function in a process, comprising: injecting said one-byte interrupt into said existing function while said process is running, wherein said injecting comprises overwriting an instruction associated with said process, said instruction existing in memory; passing control to a kernel handler upon execution of said one-byte interrupt; executing a replacement function called by said kernel handler; and returning to said code execution path.
 9. The method of claim 8, wherein said one-byte interrupt is an INT 3 interrupt instruction.
 10. The method of claim 9, wherein said kernel handler includes a mechanism to cause a return from said one-byte interrupt instruction to continue into said replacement function.
 11. The method of claim 8, further comprising inserting said one-byte interrupt such that no more than one byte in the original code in said code execution path is overwritten.
 12. The method of claim 8, further comprising loading said replacement function into a memory space accessible by said kernel handler.
 13. The method of claim 8, further comprising performing said method without requiring a reboot of a computing device on which a process executing said existing function said is running.
 14. A computer readable storage medium having computer executable instructions thereon for redirecting a code execution path in a running process, said computer executable instructions performing a method, comprising: injecting a one-byte interrupt instruction into said code execution path while said process is running, wherein said injecting comprises overwriting an instruction associated with said process, said instruction existing in memory; passing control to a kernel handler upon execution of said one-byte interrupt instruction; executing a replacement function called by said kernel handler; and returning to said code execution path.
 15. The computer readable storage medium of claim 14, wherein said one-byte interrupt is an INT 3 interrupt instruction.
 16. The computer readable storage medium of claim 14, wherein said kernel handler includes a mechanism to cause a return from said one-byte interrupt instruction to continue into said replacement function.
 17. The computer readable storage medium of claim 14, further comprising instructions for inserting said one-byte interrupt instruction such that no more than one byte in the original code in said code execution path is overwritten.
 18. The computer readable storage medium of claim 14, further comprising instructions for loading said replacement function into a memory space accessible by said kernel handler. 